Skip to content

picocrypt-ng: Add version 2.12#17903

Merged
aliesbelik merged 13 commits into
ScoopInstaller:masterfrom
scillidan:picocrypt-ng
Jun 11, 2026
Merged

picocrypt-ng: Add version 2.12#17903
aliesbelik merged 13 commits into
ScoopInstaller:masterfrom
scillidan:picocrypt-ng

Conversation

@scillidan

Copy link
Copy Markdown
Contributor

Closes #17170

  • Use conventional PR title: <manifest-name[@version]|chore>: <general summary of the pull request>
  • I have read the Contributing Guide

@coderabbitai

coderabbitai Bot commented May 27, 2026

Copy link
Copy Markdown

Review Change Stack

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

This PR adds a new Scoop Extras package manifest for Picocrypt-NG v2.12. The manifest includes version, description, homepage, GPL-3.0-or-later license, two 64-bit artifacts (portable and CLI) with targets and SHA-256 hashes, a "Picocrypt NG" shortcut, and autoupdate entries using GitHub release download URLs plus GitHub tag API-based hash discovery.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Description check ❓ Inconclusive The PR description is incomplete; it references a closed issue but lacks details about the changes and version information. Expand the description to clarify which version was added and summarize the manifest configuration changes.
✅ Passed checks (4 passed)
Check name Status Explanation
Linked Issues check ✅ Passed The linked issue #17170 requests adding Picocrypt-NG as a package; the PR adds the manifest with proper metadata, URLs, and autoupdate configuration meeting stated criteria.
Out of Scope Changes check ✅ Passed The PR introduces only the picocrypt-ng.json manifest file, which is directly in scope for the package addition request in issue #17170.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check ✅ Passed The title accurately reflects the main change: adding Picocrypt-NG package metadata for version 2.12 to the repository.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
bucket/picocrypt-ng.json (1)

1-26: Run local manifest validation before merge.

Please verify with:

scoop config debug true
scoop config gh_token <your-github-token>   # read-only token
.\bin\checkver.ps1 -App picocrypt-ng -f
.\bin\formatjson.ps1 -App picocrypt-ng
scoop install bucket\picocrypt-ng.json -a 64bit

If any checklist ambiguity comes up, use:

As per coding guidelines: “Provide clear instructions for testing the manifest locally before submission” and include contribution/wiki links for guidance.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@bucket/picocrypt-ng.json` around lines 1 - 26, Add clear local validation and
testing steps for the picocrypt-ng manifest (picocrypt-ng.json) to your PR
description or a CONTRIBUTING note: list the exact commands to run (enable
debug, set GH token, run .\bin\checkver.ps1 -App picocrypt-ng -f,
.\bin\formatjson.ps1 -App picocrypt-ng, and scoop install
bucket\picocrypt-ng.json -a 64bit), and include links to the Scoop contribution
and manifest wiki pages for guidance (ScoopInstaller/.github CONTRIBUTING.md and
Scoop Wiki App-Manifests). This ensures reviewers can reproduce manifest
validation before merge; update the PR text (not the JSON fields) to contain
those commands and links.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@bucket/picocrypt-ng.json`:
- Around line 1-26: Add clear local validation and testing steps for the
picocrypt-ng manifest (picocrypt-ng.json) to your PR description or a
CONTRIBUTING note: list the exact commands to run (enable debug, set GH token,
run .\bin\checkver.ps1 -App picocrypt-ng -f, .\bin\formatjson.ps1 -App
picocrypt-ng, and scoop install bucket\picocrypt-ng.json -a 64bit), and include
links to the Scoop contribution and manifest wiki pages for guidance
(ScoopInstaller/.github CONTRIBUTING.md and Scoop Wiki App-Manifests). This
ensures reviewers can reproduce manifest validation before merge; update the PR
text (not the JSON fields) to contain those commands and links.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 5fb45b8f-80dc-4756-b85d-457046413412

📥 Commits

Reviewing files that changed from the base of the PR and between ec31d16 and 7487bf6.

📒 Files selected for processing (1)
  • bucket/picocrypt-ng.json

@scillidan

Copy link
Copy Markdown
Contributor Author

/verify

@github-actions

Copy link
Copy Markdown
Contributor

All changes look good.

Wait for review from human collaborators.

picocrypt-ng

  • Lint
  • Description
  • License
  • Hashes
  • Checkver
  • Autoupdate

Check the full log for details.

arvdk added a commit to arvdk/Extras that referenced this pull request Jun 9, 2026
@aliesbelik

Copy link
Copy Markdown
Collaborator

/verify

@github-actions

Copy link
Copy Markdown
Contributor

Your changes did not pass all checks.

Please address the issues in the manifest and comment starting with /verify to rerun the checks.

picocrypt-ng

  • Lint
  • Description
  • License
  • Hashes
  • Checkver
  • Autoupdate

Check the full log for details.

@aliesbelik aliesbelik left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Guess manifest could provide cli version along with main app.
  • Please update to the latest version.

Comment thread bucket/picocrypt-ng.json Outdated
Comment thread bucket/picocrypt-ng.json
Comment thread bucket/picocrypt-ng.json Outdated
scillidan and others added 3 commits June 11, 2026 03:24
Co-authored-by: Aliaksandr Belik <1752374+aliesbelik@users.noreply.github.com>
Co-authored-by: Aliaksandr Belik <1752374+aliesbelik@users.noreply.github.com>

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@bucket/picocrypt-ng.json`:
- Line 36: The JSON contains invalid escape sequences `\(` and `\)` inside the
"find" regex string; update the string literal used in the "find" field (the
value starting with "sha256(Picocrypt-NG-portable.exe)...") to double-escape the
backslashes before the parentheses so they become `\\(` and `\\)`, e.g. change
"sha256\(Picocrypt-NG-portable.exe\)\\s+$sha256" to
"sha256\\(Picocrypt-NG-portable.exe\\)\\s+$sha256" and make the same change for
the other occurrence referenced in the comment.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 385bae56-6bda-4e65-a7ff-924a6d849fac

📥 Commits

Reviewing files that changed from the base of the PR and between f6abbe8 and 7e78e5b.

📒 Files selected for processing (1)
  • bucket/picocrypt-ng.json

Comment thread bucket/picocrypt-ng.json Outdated

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

♻️ Duplicate comments (1)
bucket/picocrypt-ng.json (1)

36-36: ⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Fix invalid JSON escaping in autoupdate hash regex.

Line 36 and Line 40 use \( / \), which are invalid JSON escapes and make the manifest unparsable. Use \\( and \\) in JSON string literals.

Also, please refer to the Scoop contribution docs for manifest formatting expectations:

Suggested patch
-                        "regex": "sha256\(Picocrypt-NG-portable.exe\)\\s+$sha256"
+                        "regex": "sha256\\(Picocrypt-NG-portable.exe\\)\\s+$sha256"
...
-                        "regex": "sha256\(Picocrypt-NG-cli.exe\)\\s+$sha256"
+                        "regex": "sha256\\(Picocrypt-NG-cli.exe\\)\\s+$sha256"
#!/bin/bash
set -euo pipefail

# 1) Verify JSON parses
jq empty bucket/picocrypt-ng.json

# 2) Show current regex lines for manual confirmation
rg -n '"regex":' bucket/picocrypt-ng.json

Also applies to: 40-40

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@bucket/picocrypt-ng.json` at line 36, The "regex" string literals in
picocrypt-ng.json currently contain single backslash escapes `\(` and `\)` which
are invalid in JSON; update both regex values (the "regex" entries referencing
sha256(Picocrypt-NG-portable.exe) and the other occurrence) to use double
backslashes `\\(` and `\\)` so the JSON string contains literal parentheses in
the regex, then validate the manifest parses (e.g., with jq) and re-run any
manifest linting.

Source: Linters/SAST tools

🧹 Nitpick comments (1)
bucket/picocrypt-ng.json (1)

1-46: Run local Scoop manifest validation steps before merge.

Recommended checks for this manifest (picocrypt-ng):

scoop config debug true
scoop config gh_token <your-github-token>  # read-only token
.\bin\checkver.ps1 -App picocrypt-ng -f
.\bin\formatjson.ps1 -App picocrypt-ng
scoop install bucket/picocrypt-ng.json -a 64bit
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@bucket/picocrypt-ng.json` around lines 1 - 46, Run the local Scoop manifest
validation and installation checks for the manifest "picocrypt-ng"
(bucket/picocrypt-ng.json): enable debug and set a GitHub read-only token, then
execute the checkver and formatjson scripts for the App name "picocrypt-ng" and
attempt a 64-bit install to catch autoupdate/checkver or JSON formatting issues;
if any step fails, fix the manifest fields referenced in the diff (e.g.,
"checkver", "autoupdate", "architecture.64bit.url", "architecture.64bit.hash",
"bin", "shortcuts") so checkver regexes and hashes are correct and formatjson
passes, then re-run the validation until all steps succeed before merging.

Source: Coding guidelines

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Duplicate comments:
In `@bucket/picocrypt-ng.json`:
- Line 36: The "regex" string literals in picocrypt-ng.json currently contain
single backslash escapes `\(` and `\)` which are invalid in JSON; update both
regex values (the "regex" entries referencing sha256(Picocrypt-NG-portable.exe)
and the other occurrence) to use double backslashes `\\(` and `\\)` so the JSON
string contains literal parentheses in the regex, then validate the manifest
parses (e.g., with jq) and re-run any manifest linting.

---

Nitpick comments:
In `@bucket/picocrypt-ng.json`:
- Around line 1-46: Run the local Scoop manifest validation and installation
checks for the manifest "picocrypt-ng" (bucket/picocrypt-ng.json): enable debug
and set a GitHub read-only token, then execute the checkver and formatjson
scripts for the App name "picocrypt-ng" and attempt a 64-bit install to catch
autoupdate/checkver or JSON formatting issues; if any step fails, fix the
manifest fields referenced in the diff (e.g., "checkver", "autoupdate",
"architecture.64bit.url", "architecture.64bit.hash", "bin", "shortcuts") so
checkver regexes and hashes are correct and formatjson passes, then re-run the
validation until all steps succeed before merging.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 4bb02d78-3c61-44e4-8976-e0759ca7eec1

📥 Commits

Reviewing files that changed from the base of the PR and between 7e78e5b and 4245f71.

📒 Files selected for processing (1)
  • bucket/picocrypt-ng.json

@scillidan

Copy link
Copy Markdown
Contributor Author

/verify

@github-actions

Copy link
Copy Markdown
Contributor

Your changes did not pass all checks.

Please address the issues in the manifest and comment starting with /verify to rerun the checks.

picocrypt-ng

  • Lint
  • Description
  • License
  • Hashes
  • Checkver
  • Autoupdate
  • Autoupdate Hash Extraction

Check the full log for details.

@scillidan

Copy link
Copy Markdown
Contributor Author

/verify

@github-actions

Copy link
Copy Markdown
Contributor

Your changes did not pass all checks.

Please address the issues in the manifest and comment starting with /verify to rerun the checks.

picocrypt-ng

  • Lint
  • Description
  • License
  • Hashes
  • Checkver
  • Autoupdate
  • Autoupdate Hash Extraction

Check the full log for details.

@scillidan

Copy link
Copy Markdown
Contributor Author

/verify

@github-actions

Copy link
Copy Markdown
Contributor

Your changes did not pass all checks.

Please address the issues in the manifest and comment starting with /verify to rerun the checks.

picocrypt-ng

  • Lint
  • Description
  • License
  • Hashes
  • Checkver
  • Autoupdate
  • Autoupdate Hash Extraction

Check the full log for details.

@aliesbelik

Copy link
Copy Markdown
Collaborator

/verify

@github-actions

Copy link
Copy Markdown
Contributor

All changes look good.

Wait for review from human collaborators.

picocrypt-ng

  • Lint
  • Description
  • License
  • Hashes
  • Checkver
  • Autoupdate
  • Autoupdate Hash Extraction

Check the full log for details.

@aliesbelik aliesbelik changed the title picocrypt-ng: Add version 2.09 picocrypt-ng: Add version 2.12 Jun 11, 2026
@aliesbelik aliesbelik merged commit 318c591 into ScoopInstaller:master Jun 11, 2026
3 checks passed
@scillidan

Copy link
Copy Markdown
Contributor Author

Thanks for your review!

@scillidan scillidan deleted the picocrypt-ng branch June 12, 2026 00:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Request]: Picocrypt-NG

2 participants